Methods and apparatus to make open market handsets (c.s0023-d or c.s0065-b complaint) backward compatible with old ruim cards

ABSTRACT

A method and apparatus for enabling backward compatibility in open market handsets (OMH) is provided. The method may include determining a type of an identity module based on one or more internal parameters of the identity module, and obtaining one or more credentials based at least in part on the determined the type identity module.

CROSS-REFERENCE TO RELATED APPLICATION(S)

The present application for patent claims priority to ProvisionalApplication No. 61/346,626, entitled “METHODS AND APPARATUS TO MAKE OPENMARKET HANDSETS (C.S0023-D OR C.S0065-B COMPLAINT) BACKWARD COMPATIBLEWITH OLD RUIM CARDS,” filed May 20, 2010, the contents of which areexpressly incorporated by reference herein.

BACKGROUND

1. Field

The disclosed aspects relate generally to communications between devicesand specifically to methods and systems for enabling backwardcompatibility in open market handsets (OMH).

2. Background

Advances in technology have resulted in smaller and more powerfulpersonal computing devices. For example, there currently exist a varietyof portable personal computing devices, including wireless computingdevices, such as portable wireless telephones, personal digitalassistants (PDAs) and paging devices that are each small, lightweight,and can be easily carried by users. More specifically, the portablewireless telephones, for example, further include cellular telephonesthat communicate voice and data packets over wireless networks. Further,many such cellular telephones are being manufactured with relativelylarge increases in computing capabilities, and as such, are becomingtantamount to small personal computers and hand-held PDAs.

Still further, devices may be configured as OMHs. Currently, the OMHinitiative is strategic effort aimed at enabling CDMA ecosystem with anopen market handset. 3GPP2 has two approved standards C.S0023 Rev Dversion 1.0 dated Jun. 19, 2009 (Removable User Identity Module forSpread Spectrum Systems) and C.S0065 Rev B version 1.0 dated Jan. 25,2010 “cdma2000 Application on UICC for Spread Spectrum Systems”.According to the standards, all CDMA ecosystem variables and featuresmay be represented by Elementary Files in OMH/CDMA SIM (CSIM) cards.Each Elementary File has its own standardized structure and occupiescertain amount of card memory. Further, C.S0023 compliant RUIM cards mayhave a master EF file (EF-CST: CDMA Service Table), which may indicatesupportability of different services by a removable user identity module(RUIM) card. Still further, the OMH initiative has introduced a newrevision (i.e. Rev D) of C.S0023 specification. However some operatorsprovide services that are still based on C.S0023 Rev 0 and Rev B cards.

Thus, improved apparatus and methods for enabling backward compatibilityin OMHs may be desired.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

In accordance with one or more aspects and corresponding disclosurethereof, various aspects are described in relation to enabling backwardcompatibility in OMHs. According to one aspect, a method for enablingbackward compatibility in OMHs is provided. The method can comprisedetermining a type of an identity module based on one or more internalparameters of the identity module. Further, the method can compriseobtaining one or more provisioning parameters and/or the one or morecredentials based at least in part on the determined the type identitymodule.

Another aspect relates to at least one processor configured to enablebackward compatibility in OMHs. The at least one processor includes afirst module for determining a type of an identity module based on oneor more internal parameters of the identity module. Further, the atleast one processor includes a second module for obtaining one or moreprovisioning parameters and/or the one or more credentials based atleast in part on the determined the type identity module.

Another aspect relates to a computer program product comprising acomputer-readable medium. The computer-readable medium comprising codeexecutable to determine a type of an identity module based on one ormore internal parameters of the identity module. Further, thecomputer-readable medium comprises code executable to obtain one or moreprovisioning parameters and/or the one or more credentials based atleast in part on the determined the type identity module.

Yet another aspect relates to an apparatus. The apparatus can comprisemeans for determining a type of an identity module based on one or moreinternal parameters of the identity module. Further, the apparatus cancomprise means for obtaining one or more provisioning parameters and/orthe one or more credentials based at least in part on the determined thetype identity module.

Another aspect relates to an apparatus. The apparatus can include acompatibility module operable to determining a type of an identitymodule based on one or more internal parameters of the identity module.Further, the compatibility module may be operable to obtain one or moreprovisioning parameters and/or the one or more credentials based atleast in part on the determined the type identity module.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe annexed drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed, and this description is intended to include all suchaspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements, andin which:

FIG. 1 illustrates a block diagram of a communication network accordingto an aspect;

FIG. 2 illustrates a flowchart describing an example system for enablingbackward compatibility in a OMH according to an aspect;

FIG. 3 illustrates a flowchart describing another example system forenabling backward compatibility in a OMH according to an aspect;

FIG. 4 illustrates a flowchart describing an example system forfacilitating OMH operability according to an aspect;

FIG. 5 illustrates a block diagram example architecture of acommunications device;

FIG. 6 illustrates example block diagram of a compatibility systemaccording to an aspect; and

FIG. 7 illustrates a block diagram of an example communication systemthat can enable OMH backward compatibility, according to another aspect.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details.

Generally, a user may attempt to communicate with an access networkand/or core network 125 through a communications device 110. Further,communications device 110 may coordinate with compatibility server 130to enable backward compatibility for modules and/or applicationsassociated with communications device 110. In one aspect, acommunications device 110 may include: a wireless communications device(WCD), and/or multiple devices, both wireline and wireless. For example,multiple devices may work in tandem, as a network, etc.

With reference to FIG. 1, a block diagram of a communication network 100according to an aspect is illustrated. Communication network 100 mayinclude communications devices 110 connected to an access network and/orcore network 125 (e.g., a CDMA network, a GPRS network, a UMTS network,and other types of wireline and wireless communication networks).Communication network 100 may further include a one or more of servers,such as compatibility server 130, connected to network 125.

In one aspect, communications device 110 may further includecompatibility module 112, and Virtual Card Extension Module (VCEM) 128.In one aspect, the VCEM may be described as a virtual identificationmodule. Additionally, communications device 110 may operationallyinclude removable memory card 122, such as but not limited to, aremovable user identity module (RUIM) card, a CDMA subscriber identitymodule (CSIM), etc. In one aspect, compatibility module 112 may includeinternal parameters module 114, which may include information such as,but not limited to, mobile network code (MNC), mobile country code(MCC), etc. 116. Further, VCEM 128 residing in device non-volatile (NV)memory 120 may include identity credentials 124 and profile module 126operable to assist operability, priority allocation, etc., forapplications associated with communications device 110. In one aspect,compatibility module 112 may be operable to enable features nototherwise accessible through a module and/or application associated withcommunications device 110.

In one aspect, a RUIM card 122 may be a legacy card which does not allowfor one or more functions accessible through a more to date RUIM card122 to be operable. For example, the RUIM card 122 may not allow accessto one or more features that may be otherwise accessible a 3G packetdata (3GPD) system. In such an example, instead of removing the featureto access 3GPD from the RUIM card 122, compatibility module 112 may beoperable to detect the old RUIM card 122 and fallback to read from VCEM128 for 3GPD configurations and/or user identity credentials 124.Further, in another example, if a new C.S0023 Rev D/C.S0065 Rev A orlater compliant card 122 is used, compatibility module 112 may detect akind of application first (e.g., whether the card 122 is a RUIM cardtype, CSIM card type, etc.). Thereafter, when the card 122 type isdetected as a RUIM card, compatibility module 112 may be operable todetect whether the card 122 is update or a legacy card 122. Where thecard 122 is detected to be a legacy card, user identity credentials 124may be read from VCEM 128—to provide communications device 110 withaccess to additional features.

In one aspect, detecting legacy card attributes may be performed bychecking whether a 3GPD extension (3GPD_EXTN) service (N15) is activatedin an Elementary File-CDMA service table (EF-CST). In such an aspect,when a RUIM card is inserted, compatibility module 112 may check 3GPDsimple IP (3GPD_SIP) and 3GPD mobile IP (3GPD_MIP) services in an EF-CSTand may access 3GPD credentials from RUIM card. Additionally,compatibility module 112 may check 3GPD_EXTN service (N15) in EF-CST todifferentiate legacy RUIM card (e.g., C.S0023-0 or C.S0023-B RUIMcards). In one aspect, compatibility module 112 may be operable toobtain missing information from profile module 126. In one aspect, adynamic profile may be defined as a profile which includes profileinformation from profile module 126 to augment profile informationavailable from the card 122. In another aspect, a static profile may bedefined as a fully compatible profile stored on the card 122.

In another aspect, detecting legacy card attributes may be performed bychecking an EF-revision file. In such an aspect, a EF-revision file mayprovide information related to different version of a RUIM card, (e.g.,Rev 0 as 00000000, Rev A as 00000001, Rev B as 00000010, Rev C as00000011, Rev D as 00000100, etc.). Where an operator's RUIM card havebeen configured with the same values, checking the EF-revision file mayallow compatibility module 112 to differentiate old RUIM cards and newOMH RUIM cards.

In still another aspect, detecting legacy card attributes may beperformed by checking for the presence of an EF-SIPUPPEXT (6F7D) EFitem. In such an aspect, as the EF-SIPUPPEXT was not added untilC.S0023-D standard was enacted, the presence of the EF-SIPUPPEXT elementindicates the card 122 is up to date. The above described aspectsrelated to detecting attributes of a card 122 are further discussed withrespect to FIG. 3.

In one aspect, compatibility server 130 may include credentials module132. As noted above, compatibility module 112 may access missing usercredentials 124 and/or profile information from communications device110 VCEM 128 where the information is determined to not be present inthe removable memory card 122. In one aspect, where the missing usercredentials 124 and/or profile information may not be available from thecommunications device 110 non-volatile memory 120, then communicationdevice 110 may communicate with compatibility server 130 to obtain themissing user credentials 124 and/or profile information. In such anaspect, missing user credentials 124 and/or profile information may beaccessible through credentials module 132. Further, credentials module132 may include user identity credentials module 134 to enable access tomissing user credentials, as determined by compatibility module 112.Still further, dynamic profile module 136 may include profileinformation to enable access to missing profile information, asdetermined by compatibility module 112.

As such, communications system 100 provides an environment in whichcommunications device 110 may coordinate with compatibility server 130to enable backward compatibility for modules and/or applicationsassociated with communications device 110. In one aspect, the backwardcompatibility may be accomplished through augmenting legacy removablememory cards 122 with up-to-date information and/or profiles.

FIGS. 2, 3 and 4 illustrate various methodologies in accordance withvarious aspects of the presented subject matter. While, for purposes ofsimplicity of explanation, the methodologies are shown and described asa series of acts or sequence steps, it is to be understood andappreciated that the claimed subject matter is not limited by the orderof acts, as some acts may occur in different orders and/or concurrentlywith other acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodologycould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all illustrated actsmay be required to implement a methodology in accordance with theclaimed subject matter. Additionally, it should be further appreciatedthat the methodologies disclosed hereinafter and throughout thisspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methodologies tocomputers. The term article of manufacture, as used herein, is intendedto encompass a computer program accessible from any computer-readabledevice, carrier, or media.

With reference now to FIG. 2, an example flowchart describing a system200 for enable backward compatibility for modules and/or applications isillustrated. At reference numeral 202, a change associated with anidentity module may be detected. In one aspect, the identity module maybe a RUIM card, a CSIM card, etc. In one aspect, the change may include,but is not limited to: addition of the identity module, updating theidentity module, replacing an existing identity module, etc. Atreference numeral 204, a type of identity module may be determined basedat least in part on internal parameters. In one aspect, the internalparameters may include a MNC, a MCC, an n15 element in a CST table, anEF_SIPUPPext element, etc. At reference numeral 206, additionalcompatibility credentials are obtained. In one aspect, the credentialsmay include OMH compatibility credentials, 3GPD compatibilitycredentials, etc. In one aspect, the credentials may be obtained fromnon-volatile memory associated with the device. In another aspect, thecredentials may be obtained from a compatibility server. At referencenumeral 208, the obtained credentials and the internal parameters may beused to enable the device. In one aspect, the obtained credentials andthe internal parameters may be used to generate a virtual card extensionmodule (VCEM) which provides functionality beyond what is availablethrough legacy RUIM cards.

With reference now to FIG. 3, an exemplary flowchart describing a system300 for facilitating backward compatibility for open market handsets(OMH) is illustrated. At reference numeral 302, it is determined whethera card associated with the communications device includes an n15 elementin a CST list which is both allocated and activated. In one aspect,configuration information may enable services such as, but not limitedto, voice, SMS web browsing MMS, etc.

If, at reference numeral 302, it is determined that an n15 element isallocated and activated, then at reference numeral 304 it is determinedif an EF_SIPUPPext element is present. If at reference numeral 304, itis determined that an EF_SIPUPPext element is present, then at referencenumeral 306 it is determined if the EF_SIPUPPext element is properlyconfigured. If at reference numeral 306, it is determined that theEF_SIPUPPext element is properly configured, then at reference numeral308 the communications device may access configuration information fromthe card. In one aspect, configuration information may enable servicessuch as, but not limited to, voice, SMS web browsing MMS, etc.

By contrast, if at any one of reference numerals 302, 302, or 306 it isdetermined the element is faulty and/or not present, then at referencenumeral 310 it is determined if a one or more profiles are stored on themobile equipment (ME). In one aspect, the multiple profiles may bestored in VCEM which may reside in non-volatile memory. If at referencenumeral 310 it is determined that one or more applicable profiles arestored in the communications device memory, then at reference numeral312 the communications device may access the stored profiles and operateusing the stored configuration information. In another aspect, thecommunications device may access a remote server to download theprofiles (e.g., provisioning parameters, etc.) if available and operateusing the downloaded configuration information. By contrast, if atreference numeral 310 it is determined that no applicable profiles arestored in the communications device memory (e.g., in the VCEM), then atreference numeral 312 the communications device may operate in a legacymode.

Referring to FIG. 4, an exemplary flowchart describing a system 400 forfacilitating open market handset (OMH) operability is illustrated. Atreference numeral 402, a mobile equipment (ME) may include a memory cardfrom which a mobile country code (MCC) and a mobile network code (MNC)may be obtained. In one aspect, the MCC and MNC may be read from themobile International Mobile Subscriber Identity (IMSI_M) elementary file(EF present in the card).

At reference numeral 404, the communications device may acquire anetwork connection. In one aspect, the network may allow for connectionwith a compatibility server. At reference numeral 406, it is determinedif the card is an OMH compatible card. In one aspect, the card may be aremovable user identity module (RUIM) card. In another aspect, the cardmay be a CDMA subscriber identity module (CSIM) card. In one aspect, thecard may be compatible with C.S0023-D (for RUIM) or C.S0065-A (for CSIM)standards. In such an aspect, new services may be indicated in EFs. Instill another aspect, the card may be compatible with C.S0023-0 orC.S0023-B standards. In such an aspect, an OMH handset may not be fullyoperational.

If it is determined that the memory card is OMH compatible at referencenumeral 406, then at reference numeral 408, the communications devicemay function in an OMH mode. By contrast, if it is determined that thememory card is not OMH compatible at reference numeral 406, then atreference numeral 410 it is determined that the VCEM on thecommunications device has information corresponding features availablefor an OMH mode.

If at reference numeral 410 the communications device does have thecorresponding information in the VCEM, then at reference numeral 412 thecommunications device may be operable in a synthetic OMH mode. As usedherein, a synthetic OMH mode may include a mode of operation in which aportion of OMH features are obtained from a memory card, and a differentportion of features are obtained from the VCEM. By contrast, if atreference numeral 410 the communications device does not have thecorresponding information in the VCEM, then at reference numeral 414 thecompatibility server is checked to determine if correspondinginformation is available.

If at reference numeral 414 it is determined corresponding is notavailable from the compatibility server, then at reference numeral 416the communications device may function using information available fromthe memory card. In one aspect, this operational state may be referencedto as a legacy RUIM mode. By contrast, if at reference numeral 414 it isdetermined that corresponding is available from the compatibility serverthen at reference numeral 418 the corresponding information may bedownloaded and stored in the VCEM and the communications device mayoperate in a synthetic OMH mode.

While still referencing FIG. 1, but turning also now to FIG. 5, anexample architecture of communications device 110 is illustrated. Asdepicted in FIG. 5, device 500 comprises receiver 502 that receives asignal from, for instance, a receive antenna (not shown), performstypical actions on (e.g., filters, amplifies, downconverts, etc.) thereceived signal, and digitizes the conditioned signal to obtain samples.Receiver 502 can comprise a demodulator 504 that can demodulate receivedsymbols and provide them to processor 506 for channel estimation.Processor 506 can be a processor dedicated to analyzing informationreceived by receiver 502 and/or generating information for transmissionby transmitter 520, a processor that controls one or more components ofdevice 500, and/or a processor that both analyzes information receivedby receiver 502, generates information for transmission by transmitter520, and controls one or more components of device 500.

Device 500 can additionally comprise memory 508 that is operativelycoupled to processor 506 and that can store data to be transmitted,received data, information related to available channels, dataassociated with analyzed signal and/or interference strength,information related to an assigned channel, power, rate, or the like,and any other suitable information for estimating a channel andcommunicating via the channel. In one aspect, memory 508 can includeVCEM 510. In one aspect, VCEM 510 may be used to augment user identitycredentials 512 available to the communications device 110 to provideadditional functionality. In one aspect, the VCEM 510 may includeprofile 514 module which may augment OMH compatibility credentials, 3GPDcompatibility credentials, etc.

Further, processor 506 can provide means detecting a change in theidentity module, wherein the change is either adding of a new identitymodule to the device, or changing the type of the identity module in thedevice, and means for enabling the device using the one or more internalparameters and the one or more obtained credentials.

It will be appreciated that data store (e.g., memory 508) describedherein can be either volatile memory or nonvolatile memory, or caninclude both volatile and nonvolatile memory. By way of illustration,and not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM), or flash memory. Volatile memorycan include random access memory (RAM), which acts as external cachememory. By way of illustration and not limitation, RAM is available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Memory 508 of the subject systems and methods may comprise, withoutbeing limited to, these and any other suitable types of memory.

Device 500 can further include compatibility module 530 to facilitatebackward compatibility with various legacy user identity modules 550 bydevice 500. In one aspect, compatibility module 530 may include internalparameters module 532, which may include information such as, but notlimited to, mobile network code (MNC), mobile country code (MCC), etc.Further, internal parameters module 532 may be operable to assistoperability, priority allocation, etc., for applications associated withcommunications device 500. In one aspect, compatibility module 530 maybe operable to enable features not otherwise accessible through useridentity modules 550 and/or applications associated with communicationsdevice 500.

Additionally, communications device 500 may include user interface 540.User interface 540 may include input mechanisms 542 for generatinginputs into communications device 500, and output mechanism 542 forgenerating information for consumption by the user of the communicationsdevice 500. For example, input mechanism 542 may include a mechanismsuch as a key or keyboard, a mouse, a touch-screen display, amicrophone, etc. Further, for example, output mechanism 544 may includea display, an audio speaker, a haptic feedback mechanism, a PersonalArea Network (PAN) transceiver etc. In the illustrated aspects, theoutput mechanism 544 may include a display operable to present mediacontent that is in image or video format or an audio speaker to presentmedia content that is in an audio format.

Further, in one optionally aspect, communications device 500 may includeuser identity module 550. In one aspect, user identity module mayinclude internal parameters 552, such as but not limited to, one or moreprofiles 554, MNC and MCC values 556, etc. In one aspect, the internalparameters 552 may further include an n15 element in a CST table, anEF_SIPUPPext element, etc.

It will be appreciated that user identity module 550 described hereincan be either volatile memory or nonvolatile memory, or can include bothvolatile and nonvolatile memory. By way of illustration, and notlimitation, nonvolatile memory can include read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable PROM (EEPROM), or flash memory. Volatile memorycan include random access memory (RAM), which acts as external cachememory. By way of illustration and not limitation, RAM is available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).In another aspect, user identity module 550 described herein can beremovable memory card, such as but not limited to, a removable useridentity module (RUIM) card, a CDMA subscriber identity module (CSIM),etc.

With reference to FIG. 6, illustrated is a detailed block diagram ofcompatibility system 600, such as compatibility server 130 depicted inFIG. 1. Compatibility system 600 may comprise at least one of any typeof hardware, server, personal computer, mini computer, mainframecomputer, or any computing device either special purpose or generalcomputing device. Further, the modules and applications described hereinas being operated on or executed by Compatibility system 600 may beexecuted entirely on a single network device, as shown in FIG. 6, oralternatively, in other aspects, separate servers, databases or computerdevices may work in concert to provide data in usable formats toparties, and/or to provide a separate layer of control in the data flowbetween devices, such as communications device 110, and the modules andapplications executed by Compatibility system 600.

Compatibility system 600 includes computer platform 602 that cantransmit and receive data across wired and wireless networks, and thatcan execute routines and applications. Computer platform 602 includesmemory 604, which may comprise volatile and nonvolatile memory such asread-only and/or random-access memory (ROM and RAM), EPROM, EEPROM,flash cards, or any memory common to computer platforms. Further, memory604 may include one or more flash memory cells, or may be any secondaryor tertiary storage device, such as magnetic media, optical media, tape,or soft or hard disk. Further, computer platform 602 also includesprocessor 630, which may be an application-specific integrated circuit(“ASIC”), or other chipset, logic circuit, or other data processingdevice. Processor 630 may include various processing subsystems 632embodied in hardware, firmware, software, and combinations thereof, thatenable the functionality of compatibility system 600 and the operabilityof the network device on a wired or wireless network.

Computer platform 602 further includes communications module 650embodied in hardware, firmware, software, and combinations thereof, thatenables communications among the various components of compatibilitysystem 600, as well as between compatibility system 600 andcommunications device 110. Communication module 650 may include therequisite hardware, firmware, software and/or combinations thereof forestablishing a wireless communication connection. According to describedaspects, communication module 650 may include the necessary hardware,firmware and/or software to facilitate wireless and/or wirelinecommunication between compatibility server 130 and device 110.

Memory 604 of Compatibility system 600 includes a credentials module 610which may be operable to provide a device, such as communications device110, with additional user identity credentials, profile information,etc. to facilitate backward compatibility for the communications device110. In one aspect, credentials module 604 may include user identitycredentials module 612 to enable access to missing user credentials.Still further, profile module 614 may include profile information toenable access to missing profile information. In one aspect, thecredentials may include OMH compatibility credentials, 3GPDcompatibility credentials, etc.

With reference to FIG. 7, illustrated is a system 700 for enablingbackward compatibility in OMHs, according to one aspect. For example,system 700 can reside at least partially within a communications device,user equipment, etc. It is to be appreciated that system 700 isrepresented as including functional blocks, which can be functionalblocks that represent functions implemented by a processor, software, orcombination thereof (e.g., firmware).

System 700 includes a logical grouping 702 of means that can act inconjunction. For instance, logical grouping 702 can include means fordetermining a type of an identity module based on one or more internalparameters of the identity module 704. In one aspect, the one or moreinternal parameters may include a state of a service parameter, aconfiguration parameter, etc. In another aspect, the one or moreinternal parameters may include an n15 element in a CST table, or anEF_SIPUPPext element. In such an aspect, the means for determining mayfurther include means for determining that the EF_SIPUPPext element isfaulty when at least one of: the EF_SIPUPPext element is not present, orthe EF_SIPUPPext element is not properly configured. In another aspect,the identity module can include a mobile country code (MCC) and a mobilenetwork code (MNC). In another aspect, the identity module may includeeither a RUIM or a CSIM, where a legacy identity module may be definedas a RUIM not compatible with a C.S0023-D standard, or a CSIM notcompatible with a C.S0065-A standard. In one aspect, the one or morecredentials may include: open market handset (OMH) credentials, 3Gpacket data (3GPD) credentials, etc. In another aspect, the means forobtaining may include means for using the MCC and MNC to determine theone or more credentials. In another aspect, the means for obtaining mayfurther include means for determining the one or more credentials arestored in nonvolatile (NV) memory of the device, and means for accessingthe one or more credentials stored in the NV memory of the device. Inanother aspect, the means for obtaining may further include means fordetermining the one or more credentials are available from a server, andmeans for accessing the one or more credentials from the server. Inanother aspect, the means for obtaining may further include means forobtaining a dynamic profile for an application based on the one or moreinternal parameters of the identity module, where the dynamic profileincludes one or more parameters different than the one or more internalparameters. Still further, logical grouping 702 can include means fordetecting a change in the identity module, wherein the change is eitheradding of a new identity module to the device, or changing the type ofthe identity module in the device, and enabling the device using the oneor more internal parameters and the one or more obtained credentials.Further, logical grouping 702 can include means for generating a virtualcard extension module based on the one or more internal parameters ofthe identity module and the obtained one or more credentials. Further,logical grouping 702 can include means for detecting that the identitymodule has been connected to the device, and determining that the typeof the identity module is a legacy identity module.

Additionally, system 700 can include a memory 708 that retainsinstructions for executing functions associated with the means 704 and706. While shown as being external to memory 708, it is to be understoodthat one or more of the means 704 and 706 can exist within memory 708.

As used in this application, the terms “component,” “module,” “system”and the like are intended to include a computer-related entity, such asbut not limited to hardware, firmware, a combination of hardware andsoftware, software, or software in execution. For example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a computing device and the computing device can be a component. Oneor more components can reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate by way oflocal and/or remote processes such as in accordance with a signal havingone or more data packets, such as data from one component interactingwith another component in a local system, distributed system, and/oracross a network such as the Internet with other systems by way of thesignal.

Furthermore, various aspects are described herein in connection with aterminal, which can be a wired terminal or a wireless terminal Aterminal can also be called a system, device, subscriber unit,subscriber station, mobile station, mobile, mobile device, remotestation, mobile equipment (ME), remote terminal, access terminal, userterminal, terminal, communication device, user agent, user device, oruser equipment (UE). A wireless terminal may be a cellular telephone, asatellite phone, a cordless telephone, a Session Initiation Protocol(SIP) phone, a wireless local loop (WLL) station, a personal digitalassistant (PDA), a handheld device having wireless connectioncapability, a computing device, or other processing devices connected toa wireless modem. Moreover, various aspects are described herein inconnection with a base station. A base station may be utilized forcommunicating with wireless terminal(s) and may also be referred to asan access point, a Node B, or some other terminology.

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

The techniques described herein may be used for various wirelesscommunication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and othersystems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA system may implement a radio technology such as EvolvedUTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are partof Universal Mobile Telecommunication System (UMTS). 3GPP Long TermEvolution (LTE) is a release of UMTS that uses E-UTRA, which employsOFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTEand GSM are described in documents from an organization named “3rdGeneration Partnership Project” (3GPP). Additionally, cdma2000 and UMBare described in documents from an organization named “3rd GenerationPartnership Project 2” GPP2). Further, such wireless communicationsystems may additionally include peer-to-peer (e.g., mobile-to-mobile)ad hoc network systems often using unpaired unlicensed spectrums, 602.xxwireless LAN, BLUETOOTH and any other short- or long-range, wirelesscommunication techniques.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches may also be used.

The various illustrative logics, logical blocks, modules, and circuitsdescribed in connection with the aspects disclosed herein may beimplemented or performed with a general purpose processor, a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a field programmable gate array (FPGA) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but, in the alternative, the processor may be any conventionalprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Additionally, at least oneprocessor may comprise one or more modules operable to perform one ormore of the steps and/or actions described above.

Further, the steps and/or actions of a method or algorithm described inconnection with the aspects disclosed herein may be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module may reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. An example storage medium may be coupled to theprocessor, such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor. Further, in some aspects, theprocessor and the storage medium may reside in an ASIC. Additionally,the ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal. Additionally, in some aspects, the steps and/or actionsof a method or algorithm may reside as one or any combination or set ofcodes and/or instructions on a machine readable medium and/or computerreadable medium, which may be incorporated into a computer programproduct.

In one or more aspects, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored or transmitted as one or moreinstructions or code on a computer-readable medium. Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that facilitates transfer of a computer programfrom one place to another. A storage medium may be any available mediathat can be accessed by a computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code in the form of instructions or datastructures and that can be accessed by a computer. Also, any connectionmay be termed a computer-readable medium. For example, if software istransmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs usually reproduce data optically withlasers. Combinations of the above should also be included within thescope of computer-readable media.

While the foregoing disclosure discusses illustrative aspects and/oraspects, it should be noted that various changes and modifications couldbe made herein without departing from the scope of the described aspectsand/or aspects as defined by the appended claims. Furthermore, althoughelements of the described aspects and/or aspects may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated. Additionally, all or a portion of anyaspect and/or aspect may be utilized with all or a portion of any otheraspect and/or aspect, unless stated otherwise.

1. A method of communications for a device, comprising: determining atype of an identity module based on one or more internal parameters ofthe identity module; and obtaining one or more credentials based atleast in part on the determined the type identity module.
 2. The methodof claim 1, further comprising: detecting a change in the identitymodule, wherein the change is either adding of a new identity module tothe device, or changing the type of the identity module in the device;and enabling the device using the one or more internal parameters andthe one or more obtained credentials.
 3. The method of claim 1, whereinthe one or more internal parameters comprise at least one of: a state ofa service, or a configuration parameter.
 4. The method of claim 1,wherein the one or more credentials comprise at least one of: openmarket handset (OMH) credentials, or 3G packet data (3GPD) credentials.5. The method of claim 1, wherein the identity module comprises a mobilecountry code (MCC) and a mobile network code (MNC), and wherein theobtaining further comprises using the MCC and MNC to determine the oneor more credentials.
 6. The method of claim 1, wherein the obtainingfurther comprises: determining the one or more credentials are stored innonvolatile (NV) memory of the device; and accessing the one or morecredentials stored in the NV memory of the device.
 7. The method ofclaim 1, wherein the obtaining further comprises: determining at leastone of: one or more provisioning parameters or the one or morecredentials are available from a server; and accessing the at least oneof the one or more provisioning parameters or the one or morecredentials from the server.
 8. The method of claim 1, wherein theobtaining further comprises: obtaining a dynamic profile for anapplication based on the one or more internal parameters of the identitymodule, wherein the dynamic profile includes one or more parametersdifferent than the one or more internal parameters.
 9. The method ofclaim 1, further comprising: generating a virtual identification modulebased on the one or more internal parameters of the identity module andthe obtained one or more credentials.
 10. The method of claim 1, furthercomprising: detecting that the identity module has been connected to thedevice; and determining that the type of the identity module is a legacyidentity module.
 11. The method of claim 10, wherein the identity modulecomprises either a removable user identify module (RUIM) or a CDMAsubscriber identity module (CSIM), wherein a legacy identity modulecomprises a RUIM not compatible with a C.S0023-D standard, or a CSIM notcompatible with a C.S0065-A standard.
 12. The method of claim 1, whereinthe one or more internal parameters comprise at least one of: an n15element in a CST table of RUIM; n35 element in a CST table of CSIM; oran EF_SIPUPPext element.
 13. The method of claim 12, further comprising:determining that the EF_SIPUPPext element is faulty when at least oneof: the EF_SIPUPPext element is not present; or
 14. At least oneprocessor configured to provide backward compatibility, comprising: afirst module for determining a type of an identity module based on oneor more internal parameters of the identity module; and a second modulefor obtaining one or more credentials based at least in part on thedetermined the type identity module.
 15. A computer program product,comprising: a computer-readable medium comprising: a first set of codesfor causing a computer to determine a type of an identity module basedon one or more internal parameters of the identity module; and a secondset of codes for causing the computer to obtain one or more credentialsbased at least in part on the determined the type identity module. 16.An apparatus, comprising: means for determining a type of an identitymodule based on one or more internal parameters of the identity module;and means for obtaining one or more credentials based at least in parton the determined the type identity module.
 17. The apparatus of claim16, further comprising: means for detecting a change in the identitymodule, wherein the change is either adding of a new identity module tothe device, or changing the type of the identity module in the device;and means for enabling the device using the one or more internalparameters and the one or more obtained credentials.
 18. The apparatusof claim 16, wherein the one or more internal parameters comprise atleast one of: a state of a service, or a configuration parameter. 19.The apparatus of claim 16, wherein the one or more credentials compriseat least one of: OMH credentials, or 3G packet data (3GPD) credentials.20. The apparatus of claim 16, wherein the identity module comprises amobile country code (MCC) and a mobile network code (MNC), and whereinthe means for obtaining further comprises using the MCC and MNC todetermine the one or more credentials.
 21. The apparatus of claim 16,wherein the means for obtaining further comprise: means for determiningthe one or more credentials are stored in nonvolatile (NV) memory of thedevice; and means for accessing the one or more credentials stored inthe NV memory of the device.
 22. The apparatus of claim 16, wherein themeans for obtaining further comprise: means for determining at least oneof: one or more provisioning parameters or the one or more credentialsare available from a server; and means for accessing the at least one ofthe one or more provisioning parameters or the one or more credentialsfrom the server.
 23. The apparatus of claim 16, wherein the means forobtaining further comprise: means for obtaining a dynamic profile for anapplication based on the one or more internal parameters of the identitymodule, wherein the dynamic profile includes one or more parametersdifferent than the one or more internal parameters.
 24. The apparatus ofclaim 16, further comprising: means for generating a virtualidentification module based on the one or more internal parameters ofthe identity module and the obtained one or more credentials.
 25. Themethod of claim 16, further comprising: means for detecting that theidentity module has been connected to the device; and means fordetermining that the type of the identity module is a legacy identitymodule.
 26. The apparatus of claim 25, wherein the identity modulecomprises either a removable user identify module (RUIM) or a CDMAsubscriber identity module (CSIM), wherein a legacy identity modulecomprises a RUIM not compatible with a C.S0023-D standard, or a CSIM notcompatible with a C.S0065-A standard.
 27. The apparatus of claim 16,wherein the one or more internal parameters comprise at least one of: ann15 element in a CST table of RUIM; n35 element in a CST table of CSIM;or an EF_SIPUPPext element.
 28. The apparatus of claim 27, furthercomprising: means for determining that the EF_SIPUPPext element isfaulty when at least one of: the EF_SIPUPPext element is not present; orthe EF_SIPUPPext element is not properly configured.
 29. An apparatusfor enabling backward compatibility, comprising: a compatibility moduleoperable for: determining a type of an identity module based on one ormore internal parameters of the identity module; and obtaining one ormore credentials based at least in part on the determined the typeidentity module.
 30. The apparatus of claim 29, wherein thecompatibility module is further operable for: detecting a change in theidentity module, wherein the change is either adding of a new identitymodule to the device, or changing the type of the identity module in thedevice; and enabling the device using the one or more internalparameters and the one or more obtained credentials.
 31. The apparatusof claim 29, wherein the one or more internal parameters comprise atleast one of: a state of a service, or a configuration parameter. 32.The apparatus of claim 29, wherein the one or more credentials compriseat least one of: OMH credentials, or 3G packet data (3GPD) credentials.33. The apparatus of claim 29, wherein the identity module comprises amobile country code (MCC) and a mobile network code (MNC), and whereinthe compatibility module is further operable for using the MCC and MNCto determine the one or more credentials.
 34. The apparatus of claim 29,wherein the compatibility module is further operable for: determiningthe one or more credentials are stored in nonvolatile (NV) memory of thedevice; and accessing the one or more credentials stored in the NVmemory of the device.
 35. The apparatus of claim 29, wherein thecompatibility module is further operable for: determining at least oneof the one or more provisioning parameters or the one or morecredentials are available from a server; and accessing the at least oneof the one or more provisioning parameters or the one or morecredentials from the server.
 36. The apparatus of claim 29, wherein thecompatibility module is further operable for: obtaining a dynamicprofile for an application based on the one or more internal parametersof the identity module, wherein the dynamic profile includes one or moreparameters different than the one or more internal parameters.
 37. Theapparatus of claim 29, wherein the compatibility module is furtheroperable for: generating a virtual identification module based on theone or more internal parameters of the identity module and the obtainedone or more credentials.
 38. The apparatus of claim 29, wherein thecompatibility module is further operable for: detecting that theidentity module has been connected to the device; and determining thatthe type of the identity module is a legacy identity module.
 39. Theapparatus of claim 38, wherein the identity module comprises either aremovable user identify module (RUIM) or a CDMA subscriber identitymodule (CSIM), and wherein a legacy identity module comprises a RUIM notcompatible with a C.S0023-D standard, or a CSIM not compatible with aC.S0065-A standard.
 40. The apparatus of claim 29, wherein the one ormore internal parameters comprise at least one of: an n15 element in aCST table of RUIM; n35 element in a CST table of CSIM; or anEF_SIPUPPext element.
 41. The apparatus of claim 40, wherein thecompatibility module is further operable for: determining that theEF_SIPUPPext element is faulty when at least one of: the EF_SIPUPPextelement is not present; or the EF_SIPUPPext element is not properlyconfigured.